home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01a.txt
/
000089_icon-group-sender _Wed Jul 5 09:47:32 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id JAA27523
for icon-group-addresses; Wed, 5 Jul 2000 09:47:16 -0700 (MST)
Message-Id: <200007051647.JAA27523@baskerville.CS.Arizona.EDU>
Date: Wed, 5 Jul 2000 09:40:57 -0700 (PDT)
From: Shamim Mohamed <soar@drones.com>
To: "Mark Evans" <evans@unbounded.com>
Cc: <icon-group@optima.CS.Arizona.EDU>
Subject: Re: A better GUI for the next generation
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 1035
Mark Evans <evans@unbounded.com> writes:
> Dear Iconeers, The Visual Interface Builder (VIB) has never been more
> than a toy. This note is a public encouragement to the Icon and Unicon
> development teams to drop the current VIB and consider another approach.
[...]
> Incidentally it would be nice if Unicon adopted the open source model
> more completely. Over at the Python site, I can get daily builds of the
> current development version, and its issues are openly discussed by
> Pythoneers. This is true open-source. The Icon/Unicon model is open
> source but not open source development. There are just a few people
> working on the language in their spare time, and that is why it takes so
> long.
Hmmm... sounds to me like you're volunteering. Wonderful!
The "daily build" model makes sense when many developers are actively
working on the system. In our case, there are just a few people (as you
said) - but not because we want to keep secrets. If you can help out,
why don't you drop Clint a line?
-s